Skip to content

Fix JotPluggler remote streaming#38344

Draft
seichris wants to merge 3 commits into
commaai:masterfrom
seichris:fix/jotpluggler-zmq-streaming
Draft

Fix JotPluggler remote streaming#38344
seichris wants to merge 3 commits into
commaai:masterfrom
seichris:fix/jotpluggler-zmq-streaming

Conversation

@seichris

@seichris seichris commented Jul 15, 2026

Copy link
Copy Markdown

Description

Fixes #37969.

JotPluggler passed remote addresses to MSGQ, which only accepts localhost. Remote streams now run the existing bridge in a private MSGQ namespace and subscribe on 127.0.0.1. Bridge failures are surfaced; the bridge exits and removes its namespace if its owner dies.

Verification

  • macOS build and GUI smoke
  • focused tests: 4 cases, 44 assertions
  • synthetic MSGQ -> ZMQ -> MSGQ end-to-end test
  • parent SIGKILL cleanup reproduction
  • 60 lifecycle/concurrency stress runs
  • pytest-xdist: 10 runs, 40/40 cases
  • Linux CI: all 4 JotPluggler cases passed

No comma device was available; device validation is requested before marking this ready.

@github-actions

Copy link
Copy Markdown
Contributor

Process replay diff report

Replays driving segments through this PR and compares the behavior to master.
Please review any changes carefully to ensure they are expected.

✅ 0 changed, 66 passed, 0 errors

@seichris

seichris commented Jul 15, 2026

Copy link
Copy Markdown
Author

a90e732 ran all four JotPluggler Linux tests successfully. The three red checks are unrelated fork-runner issues: unit/UI cannot load libGLESv2.so.2 (899 unit tests passed), and release packaging exceeded its 1-minute limit after completing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jotpluggler ZMQ streaming crashes

2 participants